Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Treat trait exclusively as Item not Type #744

Merged
merged 1 commit into from
Jun 17, 2022

Conversation

cburgdorf
Copy link
Collaborator

What was wrong?

This is a follow up to #710 which defined Type::Trait. Traits are currently only supported as bounds on generics. Since for the foreseeable future we do not plan to support traits in places where types are supported we should remove it from Type and instead create an Item::Trait(TraitId)

How was it fixed?

Pretty much what the description already spoiled.

@cburgdorf cburgdorf requested a review from Y-Nak June 17, 2022 08:20
let named_thing = context.resolve_name(&base.kind, desc.span)?;
resolve_concrete_trait_named_thing(context, named_thing, desc)
}
_ => panic!("Should be rejected by parser"),
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should use a special BoundDesc in the parser instead?

@cburgdorf cburgdorf force-pushed the christoph/feat/trait_as_item branch from 48d95e9 to d067633 Compare June 17, 2022 08:23
Copy link
Collaborator

@sbillig sbillig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@sbillig sbillig merged commit 9a4a2fe into ethereum:master Jun 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants